Starting VMware VirtualCenter Server service when using SQL authentication fails with the error: Login Failure, Failed to connect to database (2015824)
Symptoms
- You cannot start the VMware VirtualCenter Server service when using Microsoft SQL authentication.
- VMware VirtualCenter Server service fails to start.
- The vpxd.log file (located at C:\ProgramData\VMware\VMware Virtual Center\Logs)contains entries similar to:
T10:54:43.364-04:00 [03404 error ‘Default’] [VpxdVdb::SetDBType]: Login failure – retrying once…
T10:54:43.364-04:00 [03404 error ‘Default’] [VpxdVdb::SetDBType] Failed to connect to database: . Retry attempt: 1 …
T10:54:53.364-04:00 [03404 error ‘Default’] [VpxdVdb::SetDBType] Encountered login error. Subsequent connection attempt failed: 28000
T10:54:53.364-04:00 [03404 error ‘Default’] [VpxdVdb::SetDBType] Aborting after 1 retries.
T10:54:53.364-04:00 [03404 error ‘Default’] Error getting configuration info from the database
02-05T11:12:25.712+08:00 [02364 error ‘Default’] [VpxdVdb::SetDBType] Failed to connect to database: ODBC error: (08001) – [Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [64]. . Retry attempt: 49 …” - In the Windows Event Viewer, the VMware VirtualCenter Server service reports an error similar to:
The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
Cause
-
The VMware VirtualCenter Server service is unable to communicate with the remote database.
- There are authentication issues with the remote Microsoft SQL database when using SQL authentication.
Resolution
- Verify the DSN
- Verify Log on As in Windows for VMware VirtualCenter Server service
- Verify the database username in the registry
- Reset the encrypted password found in the#resetpwd registry
Verify the DSN
- In the Control Panel, navigate to Administrative Tools > Data Sources (ODBC) > System DSN.
- Select the vCenter Server DSN and click Configure.
- Verify the remote SQL server name, username, and default database.
- Test the connection to the SQL server.
- If it fails to connect, investigate the SQL user account used for this connection on the database server. For more information, see the Microsoft TechNet article Troubleshooting Server and Database Connection Problems.
Verify Log on As in Windows for VMware VirtualCenter Server service
- Click Start > Run, type services.msc, and click OK. The Services Management Snap-in opens.
- Right-click VMware VirtualCenter Server service and click Properties.
- Click the Log On tab.
- Verify and ensure that the Local System account option is selected.
Verify the database username in the registry
Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.
The preceding link was correct as of August 14, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.
- Take a backup of the Windows registry before proceeding.
- Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Virtualcenter\DB.
- Edit Key 2 and enter the username in the value data field.
Reset the encrypted password found in the registry
- Open a command prompt as an administrator.
- Change to the vCenter Server directory by running the command:
cd “C:\Program Files\VMware\Infrastructure\VirtualCenter Server”
Where C:\ is the drive where vCenter Server is installed. - Run the command:
vpxd.exe -p
- Enter the same password that you used while verifying the DSN connection.
- Start the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Additional Information
Note: The preceding link was correct as of August 14, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.